TS aliases doesn't play well with package.json#exports:
microsoft/TypeScript#60460
So, we had to specify each entry point separately

…s; lots of other enhancements

we already do in other places, but playground apps were an exception

…de esbuilds

…e on dev

…in manifest file; correctly reload chrome on assets change

…on in manifest file; correctly reload chrome on assets change

* feat(app-vite): generate .quasar/tsconfig.json

* feat(app-vite): generate tsconfig exclude

* feat(app-vite): add Capacitor dependencies to tsconfig paths
the Vite aliases were already there, thanks to this, TypeScript won't
complain about using Capacitor deps inside src/ anymore

* feat(app-vite): handle folder module and file aliases in tsconfig paths

* refactor(app-vite): extract tsconfig generation to a function

* feat(app-vite): generate nested path aliases for capacitor deps too
e.g. `@capacitor/dep/deep/import`

* feat(app-vite): add build.typescript.extendTsConfig hook

* feat(app-vite): create a better tsconfig, drop presets
enforce TS >=5.4 to use module: 'preserve'
forceConsistentCasingInFileNames defaults to true since TS 5.0
verbatimModuleSyntax will require user to update their codes
jsx: preserve is no longer needed for Vue Language Tools

strict: true and some of the other strict options will be added through a flag

* feat(app-vite): add an option to generate tsconfig with strict rules

compared to previous regular preset:
noUnusedLocals is turned off as it produces extra noise when using ESLint, where the behavior is better as it's configurable

compared to previous stricter config:
noPropertyAccessFromIndexSignature is removed as it doesn't even allow process.env.DEV unless it's augmented explicitly, which we don't do at the moment. It enforces process.env['DEV'] instead, which is annoying and confusing to use. We can't augment the env variables as Node types enforce string, but our own types are actual boolean values.

noImplicitReturns reduces the DX and is not that beneficial in app code compared to its use in library code. It still has it's uses, but it doesn't belong the usual strictness.

* feat(app-vite): only generate .quasar/tsconfig.json if the app has TS

* fix(app-vite): correctly handle non-existent aliases
they were throwing errors, now we skip them for an even slimmer result

* feat(create-quasar): adapt ts-vite-2  to latest specs

* fix(app-vite): suppress the esbuild tsconfig.json warning
when .quasar/tsconfig.json is missing prior to generation

* feat(app-vite): split types generation, handle it on diff
now it will re-generate the types if build.typescript or build.alias gets updated

* feat(app-vite): add prepare command
to generate tsconfig and types

* feat(create-quasar): add postinstall script to run quasar prepare

* feat(create-quasar): remove tsconfig.vue-tsc.json as it's not required anymore

* feat(app-vite): move feature flags into .quasar

* feat(create-quasar): remove unused store-flag.d.ts
as feature flags are handled into .quasar now

* docs(app-vite): document tsconfig changes

* feat(app-vite): generate declarations and vue shims

* feat(app-vite): make vue shim generation optional

* feat(create-quasar): adapt to latest TS specs

* docs(app-vite): document dts generation and feature flag changes

* docs(app-vite): correctly reference .quasar/tsconfig

* docs(app-vite): mention Capacitor TS changes

* refactor(app-vite): queue generateTypes call instead of awaiting

* docs(app-vite): enrich TS-related info in upgrade guide

* Update bex-devserver.js

* Update app-devserver.js

* Update mode.js

* feat(app-vite): generate and utilize tsconfig for JS projects too

Co-authored-by: Razvan Stoenescu <[email protected]>

---------

Co-authored-by: Razvan Stoenescu <[email protected]>

… transform aliases to ts paths; ...and other

…nsets as "rating". (#17640)

…ontent doesn't change to not uselessly force esbuild compile & apply quasar.config file changes

…pp-vite

… package exports

…CLI package exports

…eprecated (#17704)

…it gets fixed upstream

…used)

…ections)

…nitially #17698

…x.0.3

fix: 🐛 add missing comma to templates

…error